Fix combined mesh export transforms and child selection (v2.6.9)#188
Open
kyleyoungblom wants to merge 1 commit intopoly-hammer:combined-mesh-collision-transformsfrom
Conversation
|
@kyleyoungblom at a glance this looks good, but I will need to pull it into one of the repo's own branches to run the test suite on it.
Thanks! |
eaee83f to
f0a9911
Compare
- Fix collision primitive transforms (position, rotation, scale) for combined mesh exports with EMPTY display transforms - Fix visual mesh distortion when parent EMPTY has non-uniform scale/rotation set for display purposes - Add EMPTY type check to prevent non-EMPTY parents from entering combined mesh path - Skip child objects not in current View Layer to prevent selection error - Filter non-export-collection children from combined mesh exports
f0a9911 to
acc28f6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
'Ellipsis'→'EMPTY') so EMPTY parents are handled correctly in combined mesh exportsfbx_object_txvalues with EMPTY position subtraction instead of incorrect world-delta calculationsfbx_object_matrix(global_space=True)to avoid contamination from EMPTY display transforms leaking throughmatrix_localparent correction pathselect_all_childrento prevent boolean cutters and other non-export objects from being included in combined mesh exportsselect_setagainst objects not in the current View LayerTest plan